home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga MA Magazine 1998 #3
/
amigamamagazinepolishissue1998.iso
/
maksiu
/
lists
/
amoslist-1197.lzh
/
AMOSLIST
/
000201_amos-request@svcs1.digex.net_Wed Nov 19 05:58:02 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-12-04
|
3KB
Received: from svcs1.digex.net (svcs1.digex.net [204.91.197.224])
by mail3.access.digex.net (8.8.5/8.8.5) with ESMTP id FAA06475
for <mcox@access.digex.net>; Wed, 19 Nov 1997 05:58:00 -0500 (EST)
Received: (from daemon@localhost)
by svcs1.digex.net (8.8.5/8.8.5) id CAA00150
for amos-out; Wed, 19 Nov 1997 02:43:47 -0500 (EST)
Received: from mail2.access.digex.net (mail2.access.digex.net [205.197.247.3])
by svcs1.digex.net (8.8.5/8.8.5) with ESMTP id CAA00147
for <amos-list@svcs1.digex.net>; Wed, 19 Nov 1997 02:43:47 -0500 (EST)
Received: from post.mail.demon.net (post-10.mail.demon.net [194.217.242.154])
by mail2.access.digex.net (8.8.5/8.8.5) with SMTP id CAA02312
for <amos-list@access.digex.net>; Wed, 19 Nov 1997 02:43:45 -0500 (EST)
Received: from mirex.demon.co.uk ([158.152.68.125]) by post.mail.demon.net
id ab1008677; 19 Nov 97 7:40 GMT
Received: by mirex.demon.co.uk (V1.16/Amiga)
id AA002dx; Wed, 19 Nov 97 07:41:08 GMT
Date: Wed, 19 Nov 97 07:41:08 GMT
Message-Id: <9711190741.AA002dw@mirex.demon.co.uk>
Message-Id: <25665912.u10t12e.9dd6e-Braneloc@mirex.demon.co.uk>
Organization: Mirex Software
Reply-To: Braneloc@mirex.demon.co.uk
Website: http://www.mirex.demon.co.uk
From: Keith Hill <Braneloc@mirex.demon.co.uk>
To: amos-list@access.digex.net
Subject: Bubba code release imminent !!!
Status: O
X-Status:
Due to the imminent (like VERY soon) release of my level and code, what
procedures are we following for updates and other people's optimization ?
This needs to be addressed RIGHT THIS SECOND.....
I assume you'll be plugging the code into the menu, and tweaking it a
little bit, but we'll all need a copy of the final code. Perhaps we
should only send copies of the actual procedures modified by each person
for revision control ?? Comments are going to HAVE to be inserted at
the front of each procedure, and sent to all concerned. Perhaps each
procedure should have a revision number on it for safety, with each
person modifying it using a different revision number ??
Something like
procedure wave_one
' Braneloc (19/11/97)
' Giark (20/11/97) [ok]
'.... whatever.
..with the [ok] being agreed by the original programmer ??? We definately
need some kind of revision control, and I don't want my code getting out of
hand.
For reference (on my level at least) if you make any modifications to my
code (any of you), the revisions should be emailed directly to me with what
you've done, and I'll [ok] it and send on to Giark. Sound alright ??
The new demo of my level is coming very soon, and final wave design will be
shortly afterwards. I'll send another email to the list when the file goes
to Giark.
_ _ _ _ _ _ |
|_> |_| |_| |\ | |_ | | | / | | "640k should be enough for everyone"
|_> | \ | | | \| |_ |_ |_| \_ . | - Bill Gates
|
--------------+---------------
http://www.mirex.demon.co.uk
Member: IAPA & Team *AMOS*